Detached Migration

The OIRW application introduces a new Detached Migration option under the Tools main menu. This utility allows authorised users to package and deploy a migration outside the IVS environment of the source system while still using a controlled, validated workflow in the target environment.

A detached migration begins in the same way as a typical migration. The configuration packages are created, marked ready to migrate, and then added to migration sets. When a release package is created, the first screen includes a checkbox to create files for detached migration. Selecting this checkbox enables the release package to migrate outside of the IVS environment of the source environment. After the release package is created, it is built exactly as it is in a typical migration. The release package must be built and marked Ready to Promote in the source environment before it can be used for detached migration deployment in the target environment.

Deploying a Detached Migration

The Rules workbench provides a tool that manages the deployment of a detached migration. The Detached Migration utility can only be executed in the target environment after the release package has been successfully built in the source environment.

This utility enables authorised users to migrate an existing plan from a source environment to a target environment using configurable setup options, rule selection, and release management controls.

The users can create release packages, prepare them for deployment, and promote them through a guided interface that performs controlled and conflict-aware migrations into the target environment. The process ensures secure and auditable deployments while minimising operational risks and improving the efficiency of policy and product rollouts.

Steps for Detached Migration

The system displays the Tools menu in the main navigation bar when the user selects an environment in the Oracle Insurance Rules Workbench. When the user clicks the Tools icon, the system shows the Detached Migration option in the dropdown list.

Only users with detached migration security privileges can perform deployment activities in the target environment. The user must log out of the source environment and log in to the target environment before initiating the deployment process.

If the user does not select an environment, the system hides the Tools menu. This behaviour ensures that users start the detached migration workflow only after setting the correct environment and helps prevent unintended actions.

  • Log in to the Oracle Insurance Rules Workbench using valid credentials.

  • Select the target environment.

  • Navigate to the Tools area from the top-right menu and select the Detached Migration option.

  • The system displays a screen where the required details need to be added, such as: Release Package Location – File picker area

    • After deployment, the system stores the generated deployment artifacts in the configured deployment location associated with the target environment. Browse to the required Release Package file and select it. Confirm the selected file name that appears under Selected File.

    • Provide values for:

      • Package Name – Specifies the name of the release package to be created in the target environment. The package name must be unique. If a package with the same name already exists, the system displays a validation error message and prevents deployment.

      • SCM Label – Specifies the source control label associated with the migration package.

      • Comments – Allows the user to provide additional deployment-related comments.

    • Click Validate to proceed or Cancel to exit.

  • After the system successfully validates the package, it displays a validation success message. If the validation fails, the system displays an appropriate error message.


Conflict Validation

During validation, the system performs conflict checks on each rule before writing the rule data into the database. This process ensures that conflicting updates, inserts, or deletions are identified before deployment execution.

  • When the user clicks Validate and conflicts exist, the system opens a drawer that displays conflicting rules for each action type: Insert, Update, and Delete.

  • The system displays each action in a separate table and provides a context-specific message for each section.

  • Each conflicting rules table contains the following columns:

    • Rule Name

    • Rule Type

    • Source GUID

    • Target GUID

  • The drawer provides Yes and No buttons for user confirmation to continue or cancel the deployment process when conflicts are detected.

  • If the user selects No, the system aborts the detached migration process and redirects the user back to the Detached Migration main screen without deploying any changes.

Deployment

  • When the user clicks Yes, the system continues the deployment process and proceeds with the validated conflict resolution results.

  • The user clicks Deploy to start the migration process.

  • During deployment, the system creates a new non-detached release package in the target environment using the specified package name.

  • The newly created package contains all deployed migration components and maintains the association between the deployed rules and the target environment.

  • The package name must be unique within the target environment. If a package with the same name already exists, the system displays a validation error message and prevents deployment.

  • The deployment process records the associated SCM label, deployment comments, and migration metadata for tracking and auditing purposes.

  • After successful deployment, the system displays a confirmation pop-up.

  • The newly created release package becomes available in the target environment and can be used for subsequent migration activities to other environments.

  • When the user clicks No, the system redirects them to the Detached Migration main screen.